Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for v1.0.1.0 #99

Merged
merged 6 commits into from
Aug 22, 2024
Merged

Prepare for v1.0.1.0 #99

merged 6 commits into from
Aug 22, 2024

Conversation

kaBeech
Copy link
Owner

@kaBeech kaBeech commented Aug 22, 2024

No description provided.

@kaBeech kaBeech changed the title Prepare for release Prepare for v1.0.1.0 Aug 22, 2024
This is kinda silly because either we're on the 'benchmarking' branch,
in which case the executable needs more dependencies, or we're not, in
which case we don't need anything beyond base

However, if we take tensort out then we need to specify base version
ranges, which seems like it opens the possibility for error if the base
version ranges need to be updated in the future

In the future I might add the other dependencies here that appear in the
'benchmarking' branch, but they're only there to draw the chart and I
don't want to add possible dependency issues for the package as a whole.
Folks using the 'benchmarking' branch are likely smart enough to figure
out to `cabal install` if something's not working
@kaBeech kaBeech merged commit b160df7 into main Aug 22, 2024
13 checks passed
@kaBeech kaBeech deleted the prepare-for-release branch August 22, 2024 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant